Response planning and execution aiding system and method

ABSTRACT

A system for planning and executing a response to an incident includes a planning and execution data source and a processing system. The processing system is in operable communication with the planning and execution database. The processing system is configured to generate pre-planned responses to be executed by associated response assets, store data representative of the pre-planned responses in the planning and execution database, selectively retrieve a pre-planned response from the planning and execution database, communicate with the response assets associated with the retrieved pre-planned response, provide real-time tracking of the retrieved pre-planned response being executed by the associated response assets, and selectively generate recommendations for modifying the retrieved pre-planned response.

TECHNICAL FIELD

The present invention generally relates to systems and methods to moreeffectively manage responses to various events, and more particularlyrelates to a system and method to aid in the planning and execution ofresponses to various events.

BACKGROUND

The addition of aerial, robotic or electronically controlled assets to ateam of first responders such as a Special Weapons and Tactics (SWAT)team, Hazmat team can be a burden on operations requiring supplementalpersonnel to operate and manage the asset(s). The addition of theseassets should be contemplated in advance and integrated within theteam's current Concept of Operations (CONOPS) and should even absorbcurrent CONOPS activities so as to provide more effective incidentresolutions.

The integration of new assets into a common asset control for theincident commander is valued whether it is an aerial autonomous vehicle(UAV), a ground autonomous Unmanned Ground Vehicle (UGV), a canine (K9)team, a portable or stationary Unattended Ground Systems (UGS), mannedemergency vehicles, a SWAT officer, or a fireman. Incrementalfunctionality and integration with additional assets, including thosefrom other teams that may join, without incremental burden is a primeobjective.

Hence, there is a need for systems and methods to improve manned andautonomous asset association and coordination for overall incidentmanagement of team members, equipment, and remote payload sensors andsystems for the location tracking of personnel and equipment, assettracking and mission organizing of personnel and mission equipment. Thepresent invention addresses at least this need.

BRIEF SUMMARY

This summary is provided to describe select concepts in a simplifiedform that are further described in the Detailed Description. Thissummary is not intended to identify key or essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

An embodiment of a system for planning and executing a response to anincident includes a planning and execution data source and a processingsystem. The processing system is in operable communication with theplanning and execution database. The processing system is configured to:(i) generate pre-planned responses to be executed by associated responseassets, (ii) store data representative of the pre-planned responses inthe planning and execution database, (iii) selectively retrieve apre-planned response from the planning and execution database, (iv)communicate with the response assets associated with the retrievedpre-planned response, (v) provide real-time tracking of the retrievedpre-planned response being executed by the associated response assets,and (vi) selectively generate recommendations for modifying theretrieved pre-planned response.

Furthermore, other desirable features and characteristics of the systemwill become apparent from the subsequent detailed description and theappended claims, taken in conjunction with the accompanying drawings andthe preceding background.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will hereinafter be described in conjunction withthe following drawing figures, wherein like numerals denote likeelements, and wherein:

FIG. 1 depicts a functional block diagram of a response planning andexecution system;

FIG. 2 one example of the contents of each of the databases that may beused to implement the system of FIG. 1;

FIG. 3 depicts a simplified representation of various functionalmodules, systems, and sub-systems that may be used to implement thesystem of FIG. 1;

FIG. 4 depicts a functional block diagram representation of an incidentpre-planning function;

FIG. 5 depicts a functional block diagram of an incident executionfunction;

FIG. 6 depicts a state diagram of the operations implemented within acontrol function of the incident execution function; and

FIG. 7 depicts a functional block diagram of modeling and trainingfunction.

DETAILED DESCRIPTION

The following detailed description is merely exemplary in nature and isnot intended to limit the invention or the application and uses of theinvention. As used herein, the word “exemplary” means “serving as anexample, instance, or illustration.” Thus, any embodiment describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. All of the embodiments describedherein are exemplary embodiments provided to enable persons skilled inthe art to make or use the invention and not to limit the scope of theinvention which is defined by the claims. Furthermore, there is nointention to be bound by any expressed or implied theory presented inthe preceding technical field, background, brief summary, or thefollowing detailed description.

Referring now to FIG. 1, a functional block diagram of a responseplanning and execution system 100 is depicted. The depicted system 100includes a planning and execution data source 102 and a processingsystem 104. The planning and execution data source 102 includesplurality of databases. These databases include a pre-planned incidentdatabase 106, an incident area map database 108, an asset database 112,a document and standards database 114, a modeling and training database116, and an asset telemetry database 118 that receives and storestelemetry, commands, messages, and sensor feeds. It will be appreciatedthat the databases may be implemented in one or a plurality ofcomputational devices, and may be physically collocated or disposed atdifferent locations. Non-limiting examples of the content of each of thedatabases is depicted in FIG. 2, and with reference thereto will now bebriefly described.

The pre-planned incident database 106 has data stored therein that isrepresentative of a plurality of pre-planned responses to be executed byassociated response assets 122 (both personnel and equipment). Thepre-planned responses may be categorized into various types and/orregions. For example, the pre-planned response database 106 may havepre-planned response data for responding to incidents at variousenvironments, such as banks, industrial facilities, power stations orsub-stations, communication facilities, transportation facilities, andhomes, just to name a few. For each of these environments, thepre-planned response data may also include data representative of theassets (both personnel and equipment) needed to implement the response,data representative of various maps that may be needed to implement thepre-planned response, and data representative of response execution.

The incident area map database 108 contains the maps of various areas,buildings, floor plans, etc. This database 108 may receive map andenvironmental updates over any of the communication networks 124(described below). This includes environmental updates such as weatherforecasts or chemical downwind messages. The processing system 104accepts update information from the internet, intranet, or localsensors.

The asset database 112 includes data representative of the variousassets, associated IDs, associated capabilities, and various otherinformation types, such as linkage to other assets and assignments toother assets. These data can be variously provided. Some non-limitingexamples include bar-codes, RFID tags, personnel and equipment trackingdevices such as, for example, GPS, RFID, or dead reckoning modules(DRMs).

The documents and standards database 114 includes data representative ofvarious standard operating procedures (SOPs) and response doctrinetemplates from pertinent textbooks, and from lessons learned. Thisdatabase 114 may also include asset capability and limitationinformation. These data may be received and updated via any one of thecommunications networks 124.

The modeling and training database 116 includes data representative oftime sequenced responses, training videos, three dimensional (3D)interactive data, and various other data that may be used to review anddebrief prior responses, and/or validate new response plans.

The asset telemetry database 118 receives, and at least temporarilystores, data representative of real-time video, snapshots, voice, andlocation supplied from each of the assets 122.

Returning to FIG. 1, it is seen that the processing system 104 may becontinuously or selectively in operable communication with various onesof the databases 106-118 in the planning and execution data source 102.The processing system 104 may also be continuously or selectively inoperable communication with various assets 122 and one or morecommunications networks 124. The number and type of assets 122 may vary,and may include, for example, various unmanned autonomous systems 125and various manned systems 126. The unmanned autonomous systems 126 mayvary and may include, for example, one or more unmanned autonomousvehicles (UAVs), one or more unmanned ground vehicle (UGVs), variousunmanned ground sensors (UGSs), and one or more surface/submersiblesystems, just to name a few. The manned systems 128 may also vary andmay include, for example, a canine (K9) team, one or more mannedemergency vehicles, one or more police officers, fire fighters, and/orother types of first-responders, just to name a few. Each asset 122 ispreferably configured with its own computing, RF, and/or software toimplement some form of wired or wireless connectivity to the processingsystem 104, either directly or via one or more of the communicationsnetworks 124.

The communications networks 124 provide various types of information anddata to the processing system 104, and may also be used to providecommunication between one or more of the assets 122 and the processingsystem 104. It will be appreciated that the communications networks 124may vary and may include, for example, radio frequency (RF)communication networks, cellular networks, satellite communicationnetworks, an intranet, the internet, or various combinations thereof,just to name a few.

The processing system 104 is configured to implement three majorfunctions. These functions include an incident pre-planning function128, an incident execution function 132, and a modeling and trainingfunction 134. Each of these major functions 128-134 may be implementedin software, hardware, firmware, or various combinations thereof and, asnoted above, may be installed partially or wholly on one or moreindividual devices. As depicted more clearly in FIG. 3, each of thesemajor functions 128-134 intercommunicate with an automated behaviorsfunction 302, asset logic 304, and command and control (C2) networklogic functions 304. These major functions 128-134 selectively retrievedata from and store data to the databases 106-118, supply information toand receive information from a user 305 via a user interface 306, andreceive information from and supply information to the various assets122 and the communication networks 124. Each of the major functions128-134 will now be described in more detail, beginning with theincident pre-planning function 128.

The incident pre-planning function 128 selectively retrieves data fromand/or supplies data to the pre-planned incident database 106, theincident area map database 108, the asset database 112, the document andstandards database 114, and the modeling and training database 116. Theincident pre-planning function 128 is also configured to be in operablecommunication with various ones of the previously mentioned assets 122and the user interface 306. The incident pre-planning function 128 isused to plan, in advance, responses to various incidents. Morespecifically the incident pre-planning function 128 allows users, suchas incident response planners and/or commanders, to pre-plan responsesto various types of incidents at various locales. The incidentpre-planning function 128 stores the pre-planned incident responses forvarious incidents in the pre-planned incident database 106. Over time,and as incidents are responded to, users can create and update incidentresponse plans for various locations and anticipated events in theirarea of operations. When the processing system 104 is not connected toactual assets 122, the modeling and training database 116 can be used tosupport in-office planning or on-site mission rehearsal. This capabilityalleviates the need to connect to the various assets 122 whiledeveloping response plans, since, as will be described momentarily, theincident pre-planning function 128 will generate recommendationsregarding plan build-up with or without connection to actual assets 122.

In addition to the above, a user 305 can use the incident pre-planningfunction 128 upon arriving at a training or actual incident. Forexample, the user 305 can retrieve an appropriate pre-planned responsefrom the pre-planned response database 106, and use the retrievedresponse as a starting point for the training or actual incident. Whilethe incident response is being executed, the processing system 104, viafor example, an RF control device (RFCD) 412 (FIG. 4) will connect tolive elements and/or some combination of simulated elements. Thislive/simulated capability will provide the user 305 with the ability totry different scenarios or even plan, in real-time, for live eventchanges such as upcoming crew shift-changes or for other events such asanother agency arriving to help with the response. In the field duringlive events (real or training), there is a fine line betweenpre-planning and execution, and the incident pre-planning function 128transitions seamlessly between the planning and execution phases andprovides information sharing with the incident execution function 132.The incident pre-planning function 128 also works seamlessly with theassault modeling and training function 134 to support in-office planningwithout having to connect to live assets and to support real-timeplanning updates during the live event.

To implement the above-described functionality, and as shown moreclearly in FIG. 4, the incident pre-planning function 128 is configuredto implement a situational pre-planner (SPP) 402, an auto assetorganizer (AAO) 404, a status manager (SM) 406, and a team SOP (standardoperating procedure) recommender (TSR) 408. These functions, which willnow be described in more detail, provide the user 305 (such as anincident commander) with automated tools to rapidly assist in planningresponses, assembling response-appropriate assets 122, and checking thestatus of those response-appropriate assets 122.

The SPP 402 is configured to selectively retrieve data from thepre-planned incident database 106. In particular, the SPP 402 isconfigured to retrieve a list of previously created responses from thepre-planned incident database 106 for display on the user interface 306.The user 306 may then select one of the previously created responses touse as a starting point for the AAO 404.

The AAO 404 is configured, upon selection of one of the pre-plannedresponses retrieved by the SPP 402, to assemble the correct assets 122from all of the available assets, and based on expertise supplied fromthe documents and standards database 114. The AAO 404 uses assetidentifiers stored in the asset database 112. The assets 122 may beanything or anyone the user 305 believes he/she may need to complete themission. When any asset links with the RFCD 412, the system records theasset in the assets database 112.

The AAO 404 is additionally configured to implement an asset linker (AL)414 and a virtual boundary manager (VBM) 416. The AL 414 is configuredto selectively tie together various assets 122 that may not beconfigured with the ability to self-identify or self-locate. Forexample, if an individual member of a response team has a standalonecamera, the user 305 can place a barcode on the camera, scan it, andthen use the AL 414 to link it to the individual team member and his/herGPS, DRM tracker, or any other asset 122 to make the camera a “smarter”sensor that can now report its location and time along with the videofeeds. The VBM 416 allows the user 305, via the user interface 306, tographically draw and label a virtual team boundary 418. In the exampledepicted in FIG. 4, two team boundaries 418 (e.g., 418-1, 418-2) havebeen drawn and labeled.

The SM 406 is configured to receive messages, status, and events fromthe each of the assets 122 that are in operable communication with theprocessing system 104, and to maintain an on-going status chart of theassets 122 for display on the user interface 306. The SM 406 works inconjunction with a logging function implemented in the RFCD 412, andwith the asset database 112 to track the cumulative time each asset 122has logged during the incident response and other events such asenvironmental exposure. The SM 406 also works in conjunction with theincident execution function 132 (described below) to generate alertsregarding recommended shift-changes, equipment changes, and/or refreshes(such as it being necessary to charge specific battery packs, changechemical filters, or the like). The SM 406 is additionally configured totransmit asset 122 and response information (Such as the instrumentedmission elements including: who, where, when, what, sensor logs, and thenon-instrumented aspects such as the Commander's expert determination ofwhy the various events happened during the mission) to the assetsdatabase 112 to support training records, future training events andtraining needs, post-incident forensics analysis, etc.

The TSR 408 is configured to generate recommendations for the user 305.To do so, the TSR 408 implements the primary rule engine for comparinginformation in the incident area map database 108, the asset database112, the documents and standards database 114, and data supplied fromthe SM 406 to generate recommendations and alerts. The TSR 408 isconfigured to compare all of the available assets 122 within each groupto the “textbook” guidance provided in the documents and standardsdatabase 114. The TSR 408, based on this guidance, will then makerecommendations to the user 305 regarding any changes in the asset 122composition, including identifying any capabilities or equipment notpresent and provide alerts to the user 305 via the user interface 306.The TSR 408 is also configured to generate recommendations regardingassets 122 that may be present, but not normally needed to satisfy thecapability requirements of the selected pre-planned incident response.Thus identifying and offering potential weight or complexity saving forthe Commander.

The user interface 306 provides I/O screens, icons, and controls, suchas joysticks, for the user 305 to receive alerts, status, andrecommendations from the incident pre-planning function 128. The user305, via functions implemented in the user interface 306, may inputinitiation information to the incident pre-planning function 128 tobegin coordinating response teams, assets, and SOP/tactics basedrecommendations to the user 305.

The primary functions implemented in the user interface 306 includeresponse plan retrieval from the pre-planned response database 106,drawing or selecting geographic boundaries using VBM 416, an assetdrag-and-drop organization chart tool, and a team status board display.The asset drag-and-drop organization chart tool may be used to makemanual team selections, create or approve AL 414 recommendations, createor approve TSR 408 recommendations, modify existing asset configurationsbased on SM 406 updates, alerts, or as a result of shift changes or newteam members arriving on scene.

The team status board display, based on information from the SM 406,provides a near-real-time listing of the assets 122 that are assigned tospecific teams and responses. This function also provides status andlocations of assets 122 assigned to specific personnel or to the overallresponse plan. The team status board display also works with theincident execution function 132 to support asset messaging and controls.The team status board display function also outputs information to themodeling and training function 134 to support training, audits, andlitigation efforts. This provides the commander with an at-a-glancestatus, locations, and events of all assets in the current mission.

To assemble a response team using the incident pre-planning function128, the user 305 uses the user interface 306 to: 1) select the responsetype from a pull-down menu (i.e. building assault); 2) select a typicalteam configuration from the document and standards database 114 thatbest matches the current situation or pull from previous plans andconfigurations from the pre-planned response database 106; and 3)graphically draw and label a team boundary 418 on the map display fromthe incident area map database 108 loaded in his computer. He does thisfor each team as recommended by the TSR 408.

When an asset 122 stored in the assets database 112 enters a virtualteam boundary 418, the asset 122 is automatically associated with thatteam's group label. The user interface 306 will display the assets 122in each group and the associated capabilities and all equipmentassociated with those individuals.

The user 305 can then use an asset drag-and-drop tool in the userinterface 306 to make the team changes, and to send a request to otherusers 305 or Higher Headquarters for assets required to fill hissystem-identified gaps. Once the teams have been configured, the user305 can manage assets 122 as they come and go to the response location.This will support shift changes, other organizations showing up to help,or other events that change the make-up of the team. This can alsoinclude mission changes. The user can use barcodes or RFID tags with theAL 414 to rapidly join new assets 122 the asset database 112 and to thedynamically changing team groupings.

The incident execution function 132 is used to execute a selectedpre-planned response and to adjust the pre-planned response, asnecessary, in real-time. To do so, the incident execution function 132implements a response state manager. The response state manager 500,which is depicted more clearly in FIG. 5, implements various elements.The response state manager 500 receives data from three of thedatabases—the pre-planned response database 106, the incident area mapdatabase 108, and the asset database 112. The response state manager 500also receives real-time live data from the various sensors associatedwith various assets 122, and user input commands from the user interface306. The control and data flow between the various elements implementedin the response state manager 500, the databases 106, 108, 112, and thereal-time data sources, is managed via a control function 501. Forcompleteness, a state diagram of the operations implemented within thecontrol function 501 is provided, and is depicted in FIG. 6. Moreover,with reference to FIGS. 5 and 6, the control and data flow between thevarious elements implemented in the response state manager 500, thedatabases 106, 108, 112, and the real-time data sources will now bedescribed.

An actual incident response is initiated by the user 305 (e.g., acommander) before he/she arrives at the scene, and preferably while enroute to the incident scene. Based on the location and initial reportsof the incident, the user 305 can retrieve a pre-planned response fromthe pre-planned response database 108 that best matches the reportedincident (i.e., hostage barricade in a bank, chemical fire in a factory,etc.). This is accomplished via a pre-planned incident modificationaiding function 502, which uses an active incident area map 504 that wasretrieved from the incident area map database 108, and sequentialmilestone data supplied from the pre-planned incident database 106, tobegin establishing an active response state 506. Moreover, inpreparation for the response, an auto-asset tracking POI markingfunction 508 is configured to generate POIs (points of interest) 512 onthe active incident area map 504 and, as the user 305 deems necessary,to adjust asset locations 514. The system will also automaticallysuggest pre-planned incident plans associated with the location of thecommander when he activates the system outside of the home office.

The incident execution function 132 is additionally configured togenerate and display a list of desired assets 122 and to initiate anautomated call to the desired assets 122 for assistance and desiredarrival time at the incident location. Various assets 122 respond, viaone or more of the communications networks 124, regarding the ability tocomply with the requests, thereby allowing the user 305 the opportunityto adjust the response plan based on availability and capability of eachasset 122. This process continues upon arrival at the scene, as theassets 122 arrive and local communication links are established as theassets 122 are identified. This is managed via an auto-association ofassets to incident task function 516, which adjusts an active incidentasset list 518.

With all the preparations in place, the user 305 may initiate theincident response based on the pre-planned, adjusted as necessary,sequential milestones 506. A response progression tracking function 522continuously updates the location of the assets 122, and continuouslysupplies data representative thereof to the auto-asset tracking POImarking function 508. As the response progresses through the pre-plannedstages, an autonomous asset directives generation function 524 generatesalerts to be supplied to the user 305 regarding next events, assetdeviations, and also provides the user with a click-on-send function(re-position ground asset, re-position aerial asset, place intrusionsensor in a cleared room, command a human assault team to move forward).The click-on-send function also allows for critical information sharing(perpetrator location update, explosive fuel hazard, and perpetratorand/or victim photographs). This information is automatically shared onas needed basis (i.e. only the team about to encounter an explosive fuelhazard needs the alert; however, all personnel would receive photos andnumber of the perpetrator(s)).

The modeling and training function 134 may be used to test thepre-planned responses and to assess actual responses upon completion. Asdepicted in FIG. 7, the modeling and training function 134 implements aresponse tracker function 702, an after action review (AAR) function704, and an IETM (interactive electronic technical manual) function 706.Each of these functions are used for various training activitiesincluding, but not limited to, response plan training, incident arrivaltraining, incident execution training, AAR, offline embedded training,and failure insertion training (asset doesn't show up, asset fails,etc.).

The response tracker function 702 implements two major functions: datacollection and data fusion and storage. The response tracker function702 collects data transmitted to the asset telemetry database 118 fromthe various assets 122. These data may be transmitted either directlyfrom the assets 122 via wireless communication (Wi-Fi, 3G, 4G, etc.),various radio communications, or through Ethernet connectivity. Theresponse tracker function 702 securely embeds time tags within the datain order to maintain data integrity. This may be accomplished by, forexample, digitally embedding time in collected audio streams, videostreams, or images, or by encrypting all of the data into a read onlyformat.

The data fusion functionality of the response tracker function 702combines the data from the various assets and aligns these to therespective timeline in a similar fashion to a video/audio media editor.This functionality will additionally organize the collected data into anappropriate timeline and data format (e.g., video_20120713_113029.mp4,audio_20120713_113315.mp3, pic_20120713_120145.jpg) prior to storage inthe modeling and training database 116. This provides easy access to,and addition of, data in the modeling and training database 116 for useby the AAR function 704.

The AAR function 704 is configured similar to a video and audio editorin that it can combine various videos, images, and audio into a singlestream. Using the AAR function 704, the operator 305 can select eachfile to include in a project using a drag-and-drop functionality. Therecan be multiple lines of video and audio included within the project.Because, as noted above, the data are time sequenced, the operator 305can construct and combine a timeline from the data within the modelingand training database 116. The AAR function 704 may also be used to timesequence snapshots and combine the video and images from four or moresources, limited only by screen size availability. The operator 305 canselect various audio sources to be matched with events. The operator canalso change sources and repeat the timeline to be able to re-emphasize aparticular action or event from a different perspective, either audio orvideo. The operator 305 can add shapes, pointers, text or variousoverlays to highlight or point out key observations or zoom in on a keycomponent of the scenario.

The IETM function 706 is configured to allow an author to tailor theconstruction to of an IETM to a specific asset or response. Tailoring anIETM to a specific asset or response provides the user 305 with theoption of including or excluding such things as training, technicalinformation, maintenance information, operations, movies, 3Dinteractions, documentation, graphics, pictures, tables, etc. Thisprovides the author with the ability to easily load the desired filesinto a database, where the files would be translated into the IETMframework language. A constructor can then be used to organize thedatabase structure. Once an IETM has been constructed, the user 305 canmake the necessary changes to its look and feel.

As may be clear from the above, there are overlaps within each of thethree major functions implemented in the processing system 104. Forexample, assignment of assets 122 via the incident pre-planning function128 may also be used during implementation of the incident executionfunction 132 to complete a response team when various assets 122 arrive.The incident pre-planning function 128 may also use the modelingimplemented in the assault modeling and training function 134 to testand validate various response plans.

Furthermore, depending on the context, words such as “connect” or“coupled to” used in describing a relationship between differentelements do not imply that a direct physical connection must be madebetween these elements. For example, two elements may be connected toeach other physically, electronically, logically, or in any othermanner, through one or more additional elements.

Those of skill in the art will appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Some ofthe embodiments and implementations are described above in terms offunctional and/or logical block components (or modules) and variousprocessing steps. However, it should be appreciated that such blockcomponents (or modules) may be realized by any number of hardware,software, and/or firmware components configured to perform the specifiedfunctions. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present invention. For example, anembodiment of a system or a component may employ various integratedcircuit components, e.g., memory elements, digital signal processingelements, logic elements, look-up tables, or the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. In addition, those skilled inthe art will appreciate that embodiments described herein are merelyexemplary implementations.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In this document, relational terms such as first and second, and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. Numericalordinals such as “first,” “second,” “third,” etc. simply denotedifferent singles of a plurality and do not imply any order or sequenceunless specifically defined by the claim language. The sequence of thetext in any of the claims does not imply that process steps must beperformed in a temporal or logical order according to such sequenceunless it is specifically defined by the language of the claim. Theprocess steps may be interchanged in any order without departing fromthe scope of the invention as long as such an interchange does notcontradict the claim language and is not logically nonsensical.

Furthermore, depending on the context, words such as “connect” or“coupled to” used in describing a relationship between differentelements do not imply that a direct physical connection must be madebetween these elements. For example, two elements may be connected toeach other physically, electronically, logically, or in any othermanner, through one or more additional elements.

While at least one exemplary embodiment has been presented in theforegoing detailed description of the invention, it should beappreciated that a vast number of variations exist. It should also beappreciated that the exemplary embodiment or exemplary embodiments areonly examples, and are not intended to limit the scope, applicability,or configuration of the invention in any way. Rather, the foregoingdetailed description will provide those skilled in the art with aconvenient road map for implementing an exemplary embodiment of theinvention. It being understood that various changes may be made in thefunction and arrangement of elements described in an exemplaryembodiment without departing from the scope of the invention as setforth in the appended claims.

What is claimed is:
 1. A system for planning and executing a response toan incident, comprising: a planning and execution data source, theplanning and execution database comprising a pre-planned responsedatabase, an area maps database, an asset database, a documents andstandards database, a modeling and training database, and a telemetrydatabase; and a processing system in operable communication with theplanning and execution data source, the processing system configured to:(i) generate pre-planned responses to be executed by associated responseassets, (ii) store data representative of the pre-planned responses inthe planning and execution database; (iii) selectively retrieve apre-planned response from the planning and execution database, (iv)communicate with the response assets associated with the retrievedpre-planned response, (v) provide real-time tracking of the retrievedpre-planned response being executed by the associated response assets,and (vi) selectively generate recommendations for modifying theretrieved pre-planned response.
 2. The system of claim 1, wherein thepre-planned response database comprises data representative of aplurality of pre-planned responses to be executed by the associatedresponse assets.
 3. The system of claim 1, wherein the area mapsdatabase comprises data representative of various areas, buildings, andfloor plans.
 4. The system of claim 1, wherein the asset databasecomprises data representative of various assets.
 5. The system of claim1, wherein the documents and standards database comprises datarepresentative of standard operating procedures.
 6. The system of claim1, wherein the modeling and training database comprises datarepresentative of prior responses.
 7. The system of claim 1, wherein thetelemetry database comprises data representative of telemetry, commands,messages, and sensor feeds.
 8. The system of claim 1, furthercomprising: a user interface in operable communication with theprocessing system and configured to selectively render and implement oneor more I/O screens, icons, and controls.
 9. A system for planning andexecuting a response to an incident, comprising: a planning andexecution data source; and a processing system in operable communicationwith the planning and execution data source, the processing systemconfigured to: (i) generate pre-planned responses to be executed byassociated response assets, (ii) store data representative of thepre-planned responses in the planning and execution database; (iii)selectively retrieve a pre-planned response from the planning andexecution database, (iv) communicate with the response assets associatedwith the retrieved pre-planned response, (v) provide real-time trackingof the retrieved pre-planned response being executed by the associatedresponse assets, (vi) selectively generate recommendations for modifyingthe retrieved pre-planned response, and (vii) implement an incidentpre-planning function, an incident execution function, and a modelingand training function.
 10. The system of claim 9, wherein the incidentpre-planning function is configured to : generate the pre-plannedresponses to be executed by associated response assets; and store thedata representative of the pre-planned responses in the planning andexecution database.
 11. The system of claim 10, wherein the incidentpreplanning function implements a situational pre-planner, an auto assetorganizer, a status manager, and a team standard operating procedurerecommender (TSR).
 12. The system of claim 11, wherein the situationalpre-planner is configure to retrieve a list of previously createdresponses from the planning and execution data source for display on auser interface.
 13. The system of claim 12, wherein the auto assetorganizer is configured, upon selection of one of the pre-plannedresponses retrieved by the situational pre-planner, to assemble correctassets from all available assets.
 14. The system of claim 13, wherein:the auto asset is further configured to implement an asset linker (AL)and a virtual boundary manager (VBM); the AL is configured toselectively tie together various assets 122 that may not be configuredwith the ability to self-identify or self-locate; and the VBM isconfigured to allow a user, via a user interface, to graphically drawand label a virtual team boundary.
 15. The system of claim 11, whereinthe status manager is configured to: receive messages, status, andevents from the each assets that is in operable communication with theprocessing system; and maintain an on-going status chart of the assetsfor display on a user interface.
 16. The system of claim 11, wherein theTSR is configured to implement a primary rule engine to information inthe planning and execution data source to generate recommendations andalerts.
 17. The system of claim 9, wherein the incident executionfunction is configured to selectively retrieve the pre-planned responsefrom the planning and execution database, communicate with the responseassets associated with the retrieved pre-planned response, providereal-time tracking of the retrieved pre-planned response being executedby the associated response assets, and selectively generaterecommendations for modifying the retrieved pre-planned response. 18.The system of claim 17, wherein the incident execution function isadditionally configured to: generate and display a list of desiredassets; and initiate an automated call to the desired assets.
 19. Thesystem of claim 9, wherein the modeling and training function isconfigured to test the pre-planned responses and to assess actualresponses upon completion thereof.
 20. The system of claim 9, furthercomprising: a user interface in operable communication with theprocessing system and configured to selectively render and implement oneor more I/O screens, icons, and controls.